-
Notifications
You must be signed in to change notification settings - Fork 124
RSDK-12187: Store reload versions at the module and part level #5365
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RSDK-12187: Store reload versions at the module and part level #5365
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
didn't get a chance to test this on my own, but i trust your testing and the code changes seem reasonable
const reloadVersion = "reload" | ||
const ( | ||
reloadVersionPrefix = "reload" | ||
reloadSourceVersionPrefix = "reload-source" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what's the difference between these two? one is the source tarball that gets fed into cloud build, the other is the binary artifact that is produced?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup that is the difference.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
didn't test but looks good to me!
I did a lot of testing myself so I'm confident in this change. @Ethan I think lets do some testing together later in the week. Or I can handle it. After both our changes are merged in. And probably with the reload progress spinner changes if I have that merged in time. This way we can make sure everything in main across all projects works together. |
Changes how reload versions are stored and incorporates @gmulz's idea of making hot reloading storage at the part level to avoid issues if two developers hot reload the same module on different parts:
Testing
Did full round of testing to ensure the workflow passed in a preview environment along with app changes. Verified in our DB that it contained both versions while after the build finished, and then once the copy to part finished, that the source code was deleted.